Release 10.1A: OpenEdge Development:
Progress Dynamics Repository Reference

Preface

This Preface contains the following sections:

Purpose
Audience
Organization
Using this manual
Typographical conventions
OpenEdge messages

Purpose

Progress Dynamics® is a repository-based framework and application development environment (ADE) designed to accelerate the building and deployment of distributed enterprise applications. It offers you the ability to rapidly build, deploy, and customize competitive business applications using the Progress® OpenEdge® environment. By following the Progress Dynamics’ prescriptive approach, you can decrease the time required to bring your business application to deployment.

Audience

This reference is intended for developers who design applications with Progress Dynamics.

Organization

This manual is organized into chapters that outline groups of tables that serve a common purpose for the Progress Dynamics framework. The chapters are as follows:

Chapter 1 "The Progress Dynamics Repository"

Provides basic information on the design of the Repository.

Chapter 2 "Customization Group"

Describes the tables that store customization information.

Chapter 3 "Deployment and Versioning Group"

Details the tables that store deployment and versioning information.

Chapter 4 "Entity and Defaults Group"

Explains the tables that store information about entities and defaults.

Chapter 5 "Error Group"

Describes the tables that store error message information.

Chapter 6 "Globalization Group"

Examines the tables that store information used to globalize a Progress Dynamics application.

Chapter 7 "Menu and Toolbar Group"

Details the tables that store information about menus and toolbars.

Chapter 8 "Module Group"

Describes the tables that store information about modules

Chapter 9 "Multi-media and Comment Group"

Reviews the tables that store information about multi-media files and comments used in a Progress Dynamics application.

Chapter 10 "Object Group"

Describes the tables that store information about the objects in a Progress Dynamics application.

Chapter 11 "Security Group"

Explains the tables that store information about security allocations.

Chapter 12 "Sequence Group"

Describes the tables that store information about Progress Dynamics-specific sequences.

Chapter 13 "Session and Configuration Group"

Examines the tables that store session and configuration information.

Chapter 14 "Status Group"

Describes the tables that store status information.

Chapter 15 "Treeview Group"

Reviews the tables that store information used by treeviews.

Chapter 16 "User Group"

Describes the tables that store information about individual users.

Chapter 17 "User Profile Group"

Details the tables that support the use of user profiles.

Chapter 18 "Other Tables"

Describes several tables that do not fit into any group.

Chapter 19 "Legacy and Developing Structures"

Describes several groups of tables that are included in the Repository to support legacy functionality or to aid possible developments in the Progress Dynamics framework.

Appendix A "Table Names and Acronyms."

Provides a quick reference for finding the Repository table name for an FLA, or the FLA for a Repository table name.

Using this manual

This reference is intended to give you a broad view of the structure of the Progress Dynamics Repository. More specific information about table and field properties can be accessed through the Data Administration and Data Dictionary tools.

Note: This edition of OpenEdge Development: Progress Dynamics Repository Reference is based on the Repository structure including all changes up through those in icfdb020026delta.df and then through icfdb100002.df. If you have upgraded your Repository to a version that applied higher numbered delta files, check for changes made in those files.

Typographical conventions

This manual uses the following typographical conventions:

Convention	Description
Bold	Bold typeface indicates commands or characters the user types, provides emphasis, or the names of user interface elements.
Italic	Italic typeface indicates the title of a document, or signifies new terms.
SMALL, BOLD CAPITAL LETTERS	Small, bold capital letters indicate OpenEdge® key functions and generic keyboard keys; for example, GET and CTRL.
KEY1+KEY2	A plus sign between key names indicates a simultaneous key sequence: you press and hold down the first key while pressing the second key. For example, CTRL+X.
KEY1 KEY2	A space between key names indicates a sequential key sequence: you press and release the first key, then press another key. For example, ESCAPE H.
Syntax:
Fixed width	A fixed-width font is used in syntax statements, code examples, system output, and filenames.
Fixed-width italics	Fixed-width italics indicate variables in syntax statements.
Fixed-width bold	Fixed-width bold indicates variables with special emphasis.
UPPERCASE fixed width	Uppercase words are Progress® 4GL language keywords. Although these are always shown in uppercase, you can type them in either uppercase or lowercase in a procedure.
	This icon (three arrows) introduces a multi-step procedure.
	This icon (one arrow) introduces a single-step procedure.

OpenEdge messages

OpenEdge displays several types of messages to inform you of routine and unusual occurrences:

Execution messages inform you of errors encountered while OpenEdge is running a procedure; for example, if OpenEdge cannot find a record with a specified index field value.
Compile messages inform you of errors found while OpenEdge is reading and analyzing a procedure before running it; for example, if a procedure references a table name that is not defined in the database.
Startup messages inform you of unusual conditions detected while OpenEdge is getting ready to execute; for example, if you entered an invalid startup parameter.

After displaying a message, OpenEdge proceeds in one of several ways:

Continues execution, subject to the error-processing actions that you specify or that are assumed as part of the procedure. This is the most common action taken after execution messages.
Returns to the Progress Procedure Editor, so you can correct an error in a procedure. This is the usual action taken after compiler messages.
Halts processing of a procedure and returns immediately to the Progress Procedure Editor. This does not happen often.
Terminates the current session.

OpenEdge messages end with a message number in parentheses. In this example, the message number is 200:

** Unknown table name table. (200)

If you encounter an error that terminates OpenEdge, note the message number before restarting.

Obtaining more information about OpenEdge messages

In Windows platforms, use OpenEdge online help to obtain more information about OpenEdge messages. Many OpenEdge tools include the following Help menu options to provide information about messages:

Choose Help Recent Messages to display detailed descriptions of the most recent OpenEdge message and all other messages returned in the current session.
Choose Help Messages and then type the message number to display a description of a specific OpenEdge message.
In the Progress Procedure Editor, press the HELP key or F1.